Curse

pablo24 · Oct 20, 2007, 11:35 PM // 23:35

Quote:

Update - Saturday, October 20, 2007

Bug fixes
Fixed an exploit that could be used to crash the game for every player in an instance.

Guild Wars Wiki notes
This update had a bug which caused many players to be disconnected with "Error 7", and it was quickly followed by a second emergency build to fix the problem.

Nice they fixed my exploit.

It consisted into sending a health ping packet with wrong textrefs, if you try that after this update you get an error 7.

EDIT: I am quoting what Gaile stated on her talk page so that nobody gets any bad ideas.

Quote:

Originally Posted by Gaile Gray

Guys, I've been asked to let you know that anyone trying the exploit will find his/her account actioned. This would not apply to the person who made us aware of it, and if we can verify any of those test sessions (which I noted in a forum thread) that's also going to be looked at differently. But those who learned of this exploit and attempted to use it after we rolled the build will most likely find the account banned. -- Gaile 00:25, 21 October 2007 (UTC)

Quote:

Originally Posted by Gaile Gray

Some kind of crash exploit, where someone could cause another person to lose connection. I believe it was quite new, as in today. We first heard of it was this morning and no one has been able to spot its use previously (although I do believe we're going to check into that in greater detail). The exploit was disabled with a correction, as I mentioned, that also puts in place a reporting system that will allow the team to see if anyone tries to use the exploit. (I should clarify: Even if the exploit is closed, trying to use it is still disallowed by the UA, and we take that provision very seriously.) -- Gaile 08:09, 21 October 2007 (UTC)

So don't try the exploit or you risk being banned!

Molock · Oct 20, 2007, 11:37 PM // 23:37

Wow, that was a fast fix!

Thanks for having reported the exploit pablo and thanks anet for having fixed it

Red Sonya · Oct 20, 2007, 11:42 PM // 23:42

When they gonna fix that you can't report a leech in FA after the battle starts? The leech box is blank and you can't put a checkmark into it?

placebo overdose · Oct 20, 2007, 11:42 PM // 23:42

comforting to know that this problem was helped and did not evolve to a point where permenant damage was achieved

Omniclasm · Oct 20, 2007, 11:43 PM // 23:43

Yeah, I like how you can only report a leech before the battle starts. That is brilliant.

Winterclaw · Oct 20, 2007, 11:50 PM // 23:50

Quote:

It consisted into sending a health ping packet with wrong textrefs

Wrong textrefs?

Lykan · Oct 20, 2007, 11:50 PM // 23:50

Yea now you'll prob get banned like the ones who reported the ambrace exploit lol.

Red Sonya · Oct 20, 2007, 11:53 PM // 23:53

Quote:

Originally Posted by Omniclasm

Yeah, I like how you can only report a leech before the battle starts. That is brilliant.

It wasn't always that way it just started the last couple of days. Either that or these hackers have figured a way to keep themselves from being reported after the battle starts. Anet needs to look into this. The Leechers are returning to FA again.

-Loki- · Oct 20, 2007, 11:56 PM // 23:56

Quote:

Originally Posted by Lykan

Yea now you'll prob get banned like the ones who reported the ambrace exploit lol.

And they were promptly unbanned. Nice troll attempt though.

DeXyre · Oct 21, 2007, 12:18 AM // 00:18

Good find, fast fix... *thumbs up*

Swift Thief · Oct 21, 2007, 12:18 AM // 00:18

Quote:

Originally Posted by pablo24

Nice they fixed my exploit.

It consisted into sending a health ping packet with wrong textrefs, if you try that after this update you get an error 7.

What?

Divinus Stella · Oct 21, 2007, 12:25 AM // 00:25

Quote:

Originally Posted by -Loki-

And they were promptly unbanned. Nice troll attempt though.

Hardly trolling, was a valid point.

Lykan · Oct 21, 2007, 12:36 AM // 00:36

Quote:

Originally Posted by Divinus Stella

Hardly trolling, was a valid point.

Ty I thought so too. Anet ftw.

angmar_nite · Oct 21, 2007, 12:37 AM // 00:37

Remember Remember, the 20th of October...

They should do this annually now for jokes, and release GW2 on October 20 2008/9

Kha · Oct 21, 2007, 01:03 AM // 01:03

Fast fix... but no reconnects?

Divinus Stella · Oct 21, 2007, 01:34 AM // 01:34

Quote:

Originally Posted by Kha

Fast fix... but no reconnects?

Are re-connects disabled? perhaps they found another issue like the dupes.

Konrow · Oct 21, 2007, 01:38 AM // 01:38

Wow was that 24 hours or less for a fix? Very nice Anet, very nice. Good to see they fix critical errors asap.

Chthon · Oct 21, 2007, 01:58 AM // 01:58

Quote:

Originally Posted by pablo24

Nice they fixed my exploit.

It consisted into sending a health ping packet with wrong textrefs, if you try that after this update you get an error 7.

Good job Pablo. And a fast fix from a-net.

HawkofStorms · Oct 21, 2007, 02:02 AM // 02:02

Quote:

Originally Posted by angmar_nite

Remember Remember, the 20th of October...

They should do this annually now for jokes, and release GW2 on October 20 2008/9

Sigh.. a.net has to basically shut down for a few hours and everybody panics. If anybody who has played another online game will know, sever maintance and cooldowns happen VERY often in other games (like once a week WoW is shut down to be updated). A.net has some of the most stable servers I've ever seen, only being shut down like 4 times (and twice for rollbacks). That's a testament to their skill at coding since they don't have a lot of money to maintain servers.

Tactical-Dillusions · Oct 21, 2007, 03:04 AM // 03:04

Quote:

Originally Posted by Molock

Wow, that was a fast fix!

Thanks for having reported the exploit pablo and thanks anet for having fixed it

I second that. *Hands over 213 gold coins and stares at empty purse*